docs: add support contact (support@falkordb.com) and Support page#485
docs: add support contact (support@falkordb.com) and Support page#485dragnot wants to merge 9 commits into
Conversation
The docs previously had no instructions for opening a support ticket and never mentioned support@falkordb.com. Cloud tier pages advertise Community/24x7/Dedicated support without telling users how to reach it. - Add new top-level support.md page (nav_order 1000) with the support email, what to include in a ticket, Discord for community help, and info@falkordb.com for sales/general inquiries. - Add a 'Getting Support' section linking to support@falkordb.com on each cloud tier page (free, startup, pro, enterprise). More tier-specific SLA details to be added in a follow-up. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Warning Review limit reached
More reviews will be available in 16 minutes and 10 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis PR centralizes support documentation: adds a new ChangesSupport Contact Documentation
Sequence Diagram(s)sequenceDiagram
participant Reader
participant TierDoc
participant SupportPage
participant SupportEmail
Reader->>TierDoc: open tier documentation
TierDoc->>SupportPage: follow "Support" link (/support/)
Reader->>SupportPage: view contact methods (Discord, email)
Reader->>SupportEmail: send support request (support@falkordb.com)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
support.md (1)
31-31: 💤 Low valueEnsure file ends with newline.
Standard practice for text files is to end with a newline character. This helps with version control diffs and some tooling.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@support.md` at line 31, Add a trailing newline character at the end of support.md so the file ends with a single newline; open support.md and ensure the final line is terminated with "\n" (no other content changes required).
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@support.md`:
- Line 26: Update the Discord invite link text "https://discord.gg/ErBEqN9E" in
the support page to point to a non-expiring (permanent) invite; open the server
settings in Discord, create a new invite with "Never" expiration and optionally
enable a max number of uses, then replace the existing invite URL in the support
content with the newly generated permanent invite URL and verify the link
resolves.
---
Nitpick comments:
In `@support.md`:
- Line 31: Add a trailing newline character at the end of support.md so the file
ends with a single newline; open support.md and ensure the final line is
terminated with "\n" (no other content changes required).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3953e7cd-c74b-45e5-84e8-5c027a4dac66
📒 Files selected for processing (5)
cloud/enterprise-tier.mdcloud/free-tier.mdcloud/pro-tier.mdcloud/startup-tier.mdsupport.md
|
|
||
| ## Community Support | ||
|
|
||
| For general questions, usage help, and discussion, join the FalkorDB community on **[Discord](https://discord.gg/ErBEqN9E)**. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify the Discord invite link is accessible
curl -sL -w "%{http_code}" -o /dev/null "https://discord.gg/ErBEqN9E"Repository: FalkorDB/docs
Length of output: 60
Ensure the Discord invite link is configured to never expire.
The Discord link (https://discord.gg/ErBEqN9E) is currently accessible. However, ensure it is set to never expire in the Discord server settings to maintain reliable access in the documentation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@support.md` at line 26, Update the Discord invite link text
"https://discord.gg/ErBEqN9E" in the support page to point to a non-expiring
(permanent) invite; open the server settings in Discord, create a new invite
with "Never" expiration and optionally enable a max number of uses, then replace
the existing invite URL in the support content with the newly generated
permanent invite URL and verify the link resolves.
There was a problem hiding this comment.
@dragnot replace the link with https://discord.com/invite/Y2mMT9VdMy
There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
There was a problem hiding this comment.
Pull request overview
Adds a dedicated Support page and surfaces support contact instructions across FalkorDB Cloud tier docs so readers know how to reach support and what details to include.
Changes:
- Added new top-level
support.mdpage with support ticket instructions, Discord community link, and sales contact. - Added “Getting Support” sections to Cloud tier pages linking to the new Support page and listing relevant support channels.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| support.md | New top-level Support page with support/sales contact and ticket info checklist. |
| cloud/free-tier.md | Adds “Getting Support” section with support email/Discord and link to Support page. |
| cloud/startup-tier.md | Adds “Getting Support” section with support email/Discord and link to Support page. |
| cloud/pro-tier.md | Adds “Getting Support” section highlighting 24/7 support and linking to Support page. |
| cloud/enterprise-tier.md | Adds “Getting Support” section highlighting dedicated support and linking to Support page. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ## Getting Support | ||
|
|
||
| Need help? Email **[support@falkordb.com](mailto:support@falkordb.com)** to open a support ticket, or join the community on **[Discord](https://discord.gg/ErBEqN9E)**. See the [Support page]({{ site.baseurl }}/support/) for more details. |
There was a problem hiding this comment.
|
|
||
| ## Getting Support | ||
|
|
||
| Need help? Email **[support@falkordb.com](mailto:support@falkordb.com)** to open a support ticket, or join the community on **[Discord](https://discord.gg/ErBEqN9E)**. See the [Support page]({{ site.baseurl }}/support/) for more details. |
There was a problem hiding this comment.
free DBs can open a support ticket, its ok
|
|
||
| ## Getting Support | ||
|
|
||
| Need help? Email **[support@falkordb.com](mailto:support@falkordb.com)** to open a support ticket, or join the community on **[Discord](https://discord.gg/ErBEqN9E)**. See the [Support page]({{ site.baseurl }}/support/) for more details. |
There was a problem hiding this comment.
yes thats the goal, every customer and prospect can open a support ticket
|
@alexberesnev @shahar-biron please approve or reject @guy |
|
|
||
| ## Community Support | ||
|
|
||
| For general questions, usage help, and discussion, join the FalkorDB community on **[Discord](https://discord.gg/ErBEqN9E)**. |
There was a problem hiding this comment.
@dragnot replace the link with https://discord.com/invite/Y2mMT9VdMy
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Drop the Instance Type column from the Standalone and Replicated tables and left-align the remaining columns. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@copilot resolve the merge conflicts in this pull request |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
# Conflicts: # cloud/pro-tier.md
Resolved the merge conflicts by merging |
Remove the unrelated Pro Tier table edits from this PR. The Instance Type column removal is now tracked separately in PR #496. This branch only adds the Getting Support section to the Pro Tier page. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@gkorland all changes should be ok, lets close this if you are good with this |
Summary
The docs currently have no instructions for opening a support ticket, and
support@falkordb.comis not mentioned anywhere. The cloud tier pages advertise Community / 24/7 / Dedicated support but never tell readers how to actually reach support. This PR closes that gap.Changes
support.md(nav_order 1000, permalink/support/) — single source of truth for support contact:support@falkordb.com).info@falkordb.comfor sales / general inquiries.cloud/free-tier.md,cloud/startup-tier.md,cloud/pro-tier.md,cloud/enterprise-tier.md— added a short "Getting Support" section to each tier page with the support email and a link to the new Support page. Pro and Enterprise sections call out their support level (24/7 and Dedicated).Tier-specific SLAs and additional details will be added in a follow-up PR.
Testing
N/A — documentation-only change. No code, build, or test impact.
Memory / Performance Impact
N/A.
Related Issues
None.
Summary by CodeRabbit